Communications centric management platform

ABSTRACT

The disclosed embodiments include a computer-implemented method for communications centric care. A caregiver interface serves a patient interface in accordance with a disease management program to collaboratively lead the patient to recover from a disease. The method can include obtaining content items relating to a patient and labeling each content item as either a secure content item or an unsecure content item, and then comparing the labels with identifiers of the patient, the caregiver, and/or a schedule key events of the disease management program. The content items are selectively bifurcated for the patient and/or caregiver interfaces. As such, the interfaces can manage communications in accordance with the disease management program.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication No. 62/841,465, filed May 1, 2019, titled“Communication-Centered Care Management Platform,” which is incorporatedherein by reference in its entirety.

TECHNICAL FIELD

The disclosed teachings generally relate to a communicationsarchitecture. The disclosed teachings more particularly relate to anarchitecture for communications management of a primary interface for aprimary user and a secondary interface for a secondary user, where thesecondary user supports the primary user.

BACKGROUND

Disease management is a system of coordinated healthcare interventionsand communications for populations with conditions in which patientself-care efforts are significant. Successful disease managementrequires sharing relevant information in a structured manner amongstakeholders. However, stakeholders are people with differentperspectives, who have access to different sources of information, andcommunicate in different ways. For example, a patient's perspective canvastly differ from a familial supporter, which can vastly differ from aprofessional caretaker. The waves of emotions in a disease managementjourney can negatively impact how patients care for themselves and howcaregivers care for the patients. Further, the information that couldaid in disease management is scattered all over the internet or onlyaccessible to some stakeholders. Tracking pieces of informationdiscovered by stakeholders is nearly impossible, and unstructuredresearch and communications can result in redundant information thatinundates patients and caregivers, creates daunting expectations, andresults in isolation. Moreover, caregivers and patients suffer when theystumble through trial and error to find solutions that work. This is amajor drawback in disease management because timely communications ofkey information between a patient and a caregiver is critical for thepatient to complete a disease management journey with a successfuloutcome. Thus, typical disease management involves unstructured,untimely, and inconsistent communications of unreliable information.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features and attributes of the disclosed technology will becomemore apparent to those skilled in the art from a study of the DetailedDescription in conjunction with the drawings. Embodiments of thedisclosed technology are illustrated by way of example and notlimitation in the drawings, in which like references indicate similarelements.

FIG. 1 is a flowchart that illustrates a process implemented by acommunications centric platform.

FIG. 2 is a block diagram that illustrates an layered architecture ofthe platform.

FIG. 3 is a block diagram that illustrates a system that implements theplatform.

FIG. 4 is a block diagram that illustrates an architecture of acommunications management engine.

FIG. 5 is a flowchart that illustrates a process for building journeysfor different diseases.

FIGS. 6A through 6D show side-by-side screen views of managedcommunications that are bifurcated for a patient and a caregiver.

FIG. 7 is a flowchart of a process for managing communications between apatient and a caregiver.

FIG. 8 is a block diagram that depicts components of the platform.

FIG. 9 is a block diagram that illustrates an example computing devicein which aspects of the disclosed technology can be embodied.

The drawings depict various embodiments for the purpose of illustrationonly. Those skilled in the art will recognize that alternativeembodiments may be employed without departing from the principles of thetechnology. Accordingly, while specific embodiments are shown in thedrawings, the technology is amenable to various modifications.

DETAILED DESCRIPTION

The embodiments set forth below represent necessary information toenable those skilled in the art to practice the embodiments andillustrate the best mode of practicing the embodiments. Upon reading thefollowing description in light of the accompanying figures, thoseskilled in the art will understand the concepts of the disclosure andwill recognize applications of concepts that are not particularlyaddressed herein. It should be understood that these concepts andapplications fall within the scope of the disclosure and theaccompanying claims.

Embodiments may be described with reference to particular computerprograms, system configurations, networks, etc. However, those skilledin the art will recognize that these features are equally applicable toother computer program types, system configurations, network types, etc.For example, although the term “Wi-Fi network” may be used to describe anetwork, the relevant embodiment could be deployed in another type ofnetwork.

Moreover, the disclosed technology can be embodied using special-purposehardware (e.g., circuitry), programmable circuitry appropriatelyprogrammed with software and/or firmware, or a combination ofspecial-purpose hardware and programmable circuitry. Accordingly,embodiments may include a machine-readable medium having instructionsthat may be used to program a computing device (e.g., mobile phone, anetwork-connected computer server) to exchange communications, classifydata items to determine an appropriate action, and perform theappropriate action.

Terminology

The purpose of terminology used herein is only for describingembodiments and is not intended to limit the scope of the disclosure.Where context permits, words using the singular or plural form may alsoinclude the plural or singular form, respectively.

As used herein, unless specifically stated otherwise, terms such as“processing,” “computing,” “calculating,” “determining,” “displaying,”“generating,” or the like, refer to actions and processes of a computeror similar electronic computing device that manipulates and transformsdata represented as physical (electronic) quantities within thecomputer's memory or registers into other data similarly represented asphysical quantities within the computer's memory, registers, or othersuch storage medium, transmission, or display devices.

As used herein, terms such as “connected,” “coupled,” or the like, mayrefer to any connection or coupling, either direct or indirect, betweentwo or more elements. The coupling or connection between the elementscan be physical, logical, or a combination thereof.

References to “an embodiment” or “one embodiment” means that theparticular feature, function, structure, or characteristic beingdescribed is included in at least one embodiment. Occurrences of suchphrases do not necessarily refer to the same embodiment, nor are theynecessarily referring to alternative embodiments that are mutuallyexclusive of one another.

Unless the context clearly requires otherwise, the words “comprise” and“comprising” are to be construed in an inclusive sense rather than anexclusive or exhaustive sense (i.e., in the sense of “including but notlimited to”).

The term “based on” is also to be construed in an inclusive sense ratherthan an exclusive or exhaustive sense. Thus, unless otherwise noted, theterm “based on” is intended to mean “based at least in part on.”

The term “module” refers broadly to software components, hardwarecomponents, and/or firmware components. Modules are typically functionalcomponents that can generate useful data or other output(s) based onspecified input(s). A module may be self-contained. A computer programmay include one or more modules. Thus, a computer program may includemultiple modules responsible for completing different tasks or a singlemodule responsible for completing multiple tasks.

The term “managed communications” broadly refers to a form ofstructuring communications among members of a group to, for example, aidin achieving a desired outcome. In one example, a communications centricplatform provides pipelines for structuring communications between apatient and a caregiver. For example, the pipelines can bifurcate secureand unsecure information such that information is securely sharedbetween a patient and a caregiver in a seemly open environment. As such,the patient and caregiver engage in structured communications that seemnatural.

When used in reference to a list of multiple items, the word “or” isintended to cover all of the following interpretations: any of the itemsin the list, all of the items in the list, and any combination of itemsin the list.

The sequences of steps performed in any of the processes describedherein are exemplary. However, unless contrary to physical possibility,the steps may be performed in various sequences and combinations. Forexample, steps could be added to, or removed from, the processesdescribed herein. Similarly, steps could be replaced or reordered. Thus,descriptions of any processes are intended to be open-ended.

The disclosed embodiments include a communications centric platform(“platform”) that manages communications in a structured manner toadvance members of a group towards a common objective. Examples of thecommunications include electronic text, images, or the like. In oneexample, the platform initiates and manages an instant message dialoguebetween computing devices of a patient, caregiver, or other members of agroup. The communications conform with a schedule of structured eventsto achieve an improved health outcome for the patient.

The platform can identify a suitable disease management journey for aparticular patient, where the journey includes a schedule of key eventstypically experienced by similarly situated patients. For example, amachine learning model can process user-generated data to identify alikely journey for a patient from among multiple journeys. The journeyhas a particular structure of key events to stage timely content thatmay be personalized for a patient's recovery. The platform also allowsusers to create closed communities (e.g., including loved ones, peers,mentors) that foster hope, engagement, and emotional well-being atpoints in time of key events to help advance the common objective ofimproving the health outcome of the patient.

That is, the platform connects members of the closed group with othermembers to form larger support networks that aid in advancing multipleobjectives. For example, the platform can help connect caregivers ofdifferent closed groups to create practical and emotional supportnetworks that address caregiver health and well-being concerns. Theplatform can further serve to reassure and build confidence incaregivers that feel alone, overwhelmed, and responsible for makingdifficult decisions.

The platform can also help educate members of groups. In particular, theplatform can help patients regain a sense of control over their care byeducating on next steps that can reduce unnecessary visits andreadmissions. The platform also engages and activates members of agroup. For example, the platform improves engagement by helping patientsand caregivers to create meaningful relationships with managedcommunications. As a result, the platform improves patient experience byintegrating with systems and resources to create a connected, seamlesstreatment that drives user stickiness and loyalty while managingcommunications to achieve a collective objective.

FIG. 1 is a flowchart that illustrates a process implemented by acommunications centric platform. As shown, the platform separates usersinto roles 102, where each role has one or more data access rights andprovides certain communications. A patient role or caregiver role canhave a first set of data access rights that include access privatehealthcare data and private personal data. The patient can have controlover who gets granted access to the private data. The patient can granta caregiver with access to certain private data. The communications fromusers in this role are managed to keep other users informed, engaged andparticipating in the patient's disease management.

A healthcare professional role (e.g., doctor) can have a second set ofdata access rights that are different from the first set of data accessrights. For example, the healthcare professional can have access toprivate medical data while being denied access to personalcommunications of the patient that are part of the recovery process. Thecommunications of users in this role are managed to keep dataaccessible, well-organized, and responsive.

A community role can have a third set of data access rights that aredifferent from the first and second sets of data access rights. Forexample, the community role may not have any automatic data accessright. Instead, a user with a community role can only see data that isdirectly shared by the patient or caregiver. In other words, thecommunity role does not have any independent visibility intocommunications. The communications of users in this role are managed toprovide support, education, and emotional well-being of other users.

The communications from users of different roles 102 are processedthrough a communications management engine 104 (“engine 104”). Theengine 104 functions to harmonize the communications (e.g., messages,data) to conform with the structure of the journey of a patient'srecovery. For example, users in the community role may communicatefreely with both patients and caregivers to provide support andeducation. In contrast, users that are healthcare professionals may onlycommunicate with the patient and authorized caregivers to maintain thepatient's privacy. The engine 104 is operated in accordance withoutcomes objectives, which can include rules, policies, conditions, etc.Thus, the outcomes objectives drive the communications management engine104 to manage the communications of users that have different roles 102.The management of communications is based on the structure illustratedin FIG. 1 and prioritizes those building blocks in a manner thatimproves communications for care teams of patients and caregivers.

FIG. 2 is a block diagram that illustrates a layered structure of theplatform 200. As shown, a foundational layer for managed communicationsis the journey 202, which is based on a disease management plan. Thecommunications of the care team 204 (e.g., patient, caregiver) aremanaged in accordance with the journey 202 A similar patients 206 layeris above the care team 204, and a peer mentors 208 layer is above thesimilar patients 206. The similar patients 206 layer includes users ofthe platform that are simultaneously having a similar experience as thepatient, and the peer mentors 208 layer includes users that have alreadyhad a similar experience as the patient. The layering can define thelevel of access rights to data or degrees of visibility into data. Forexample, peer mentors 208 can have less visibility to private datacompared to the care team 204. The layers above the peer mentors 208include a health worker 210, mid-level provider 212, and top-levelprovider 214.

The engine can bridge communications between the home-sideinterconnections and service-side interconnections. In some embodiments,the health worker population or any of the healthcare providers can bevirtual providers. In one embodiment, the platform can managecommunications with role dependent visibility. That is, user interfacesof the platform can vary for each role such that a doctor has a view ofan interface that presents information that identifies the patientwhereas the view of the interface for a health worker may only provideaccess to non-identifying information.

FIG. 3 is a block diagram that illustrates a system 300 that implementsthe platform. The system 300 manages communications that are shared ondevices operated by the patient and other stakeholders of a diseasemanagement journey. As shown, the communications management engine 302(“engine 302”) can manage communications that are shared among a patientdevice 304 and other stakeholder devices 306 over networks 308. Theengine 302 may administer a mechanism that improves the engagement bythe patient of the patient device 304 to complete a communication flowbetween a patient and caregiver. In some embodiments, the mechanismcould be part of a portal that allows users to exchange informationrelated to a patient's medical condition. Examples of the portal includea website, mobile app, or any communications mechanism.

The engine 302 can implement a disease management journey that iscustomized for a patient by applying information about the patient toalgorithm(s). For example, the patient's background information andcontextual information can cause the communications management engine tocontrol information that is available to stakeholder devices 306. Insome embodiments, contextual information could be derived from userinputs and applied to algorithm(s) to improve the communicationsmanagement. Further still, information obtained from sources other thanpatient device 304 can be used to engage the patient to provideadditional useful information for algorithm(s) that implement thejourney.

Each component of the system 300 may include combinations of hardwareand/or software to process data or information, perform functions,communicate over the networks 308, etc. For example, any component ofthe system 300 may include a processor, memory or storage, a networktransceiver, a display, OS and application software (e.g., for providinga user interface), and the like. Other components, hardware, and/orsoftware included in the system 300 that would be well known to personsskilled in the art are not shown or discussed herein for the sake ofbrevity. The networks 308 can include any combination of private,public, wired, or wireless portions. The data or informationcommunicated over the networks 308 may be encrypted or unencrypted atvarious locations or along different portions of the networks 308.

The patient device 304 and stakeholder devices 306 (collectivelyreferred to as “user devices”) can exchange communications over thesystem 300 through the communications management engine 302. Examples ofpatient devices 304 and stakeholder devices 306 include smartphones(e.g., GOOGLE PIXEL, APPLE IPHONE, SAMSUNG GALAXY), tablet computers(e.g., APPLE IPAD, MICROSOFT SURFACE), computers (e.g., GOOGLECHROMEBOOK, APPLE MACBOOK, LENOVO THINKPAD), and any other device thatis capable of exchanging data with the over the networks 308. Forexample, a mobile device operated by a patient can communicate with acaregiver via a disease management app running on the patient device304.

The user devices can include a global positioning system (GPS) receiverthat receives positioning signals used to determine the geographiclocation of the user device. The determined geographic location can besubmitted to the engine 302 to influence selection of a recommendedscreen view for a patient or stakeholder based on the location of theuser device. For example, an automatic communication could be invoked onthe patient device 304 when the location of the patient device 304 is ahospital.

The engine 302 may execute on any number of server computers thatoperate to perform processes such as determining a journey based oninputs and contextual information related to a patient's healthcondition. The engine 302 operates to engage users of the user devicesin accordance with a communication mode. The collected data and/orinformation is managed to further the patient and stakeholders towardsan outcome. The engine 302 can execute algorithms for managingcommunication flows among patients and other stakeholders. For example,a communication algorithm may include a combination of rules forselecting types and forms of communications for the patient at aparticular point in time of a patient's journey.

A set of rules of a communication management algorithm can customizedfor the patient's disease management journey as prescribed by ahealthcare professional. A communication management algorithm mayinclude a combination of rules for selecting a suitable communicationflow. In some embodiments, any of the disclosed algorithms may includepolicies having rules, criteria, conditions, and/or thresholds that areset in accordance with a disease management protocol to apply thepolicies in a manner that is personalized for a patient. For example, acommunication algorithm may include a rule set based on a firstpatient's gender, age, and a diagnosed condition. Another communicationalgorithm for a second patient may include a different set of rulesbased on that patient's demographics.

The data input by a user of a user device engaged in acommunication-centered care may be communicated automatically to thepatient's healthcare provider upon establishing a direct connection sothat the healthcare provider can seamlessly aid the user. Accordingly,data from healthcare providers, other devices, or services can beprovided by the stakeholder devices 306 over the networks 308 throughthe engine 302.

The stakeholder devices 306 may include any number of servers or othercomputing resources that can collect, store, and/or provide data orinformation to the engine 303 over the networks 308 for use in the careof a patient. The stakeholder devices 306 may include any source ofhealth-related information. For example, the stakeholder devices 306 mayinclude any devices operated by providers such as medical facilities,private offices, or devices administered by healthcare professionals. Insome embodiments, the data or information may include at least portionsof medical records utilized in medical algorithms. The stakeholderdevices 306 may include contextual information related to or affectingthe diabetic condition of a patient obtained from a variety of devices.

FIG. 4 is a block diagram that illustrates an architecture 400 of acommunications management engine. The platform can leverage capabilitiesof other features or products to improve usability. This includesintegration of machine learning capabilities to obtain medical data andidentify potential issues, integration with search engines to search forrelevant health related data, a natural language processing interfacefor search and data structure for content, the ability to pull data fromthird party devices such as fitness devices, instant messengercapabilities including chat-based conversation tools, communication userinterfaces (e.g., both visual and interactive), and experience in acombination of both chatbot and a human-chat interface.

The architecture 400 includes data sources 402 that are accessible forcapabilities 404. The data sources 402 include a data sources outsidethe integrated delivery system 405 (“outside data sources 405”) and datasources of the integrated delivery system 406. The outside data sources405 include a medical knowledge repository 408, insurance information410, patient provided information 412, health search knowledgebase 414and community posts 416. The data sources of the integrated deliverysystem 406 include clinical data 418, annotated notes 420, appointmentsor scheduling 422, and provider specific resources 424.

The capabilities 404 include an AI-powered virtual assistant 426,natural language processor 428, speech-to-text 430, data analysis 432,predictive analytics 434, and translations 436. As such, the platformcan integrate home based features and service providers. For example, onthe home-side, the platform can display journey-specific content basedon a user role, help coordinate activities amongst caregivers, connectto home devices and generate alerts, control home devices, and displaydevice captured data in a profile. On the provider-side, the platformcan link with electronic medical record data sources to obtain labs andimaging data, suggest and store questions for a care team, capture andtrack care data, and create provider facing profiles including symptoms.

The platform manages the communications of a patient and the patient'scaregiver to engage in a manner that conforms to key events of thepatient's disease management journey. The communications are managed tofoster strong, meaningful relationships to keep users coming back tocontinue conversations. The disclosed embodiments enable discovery ofjourneys for users to experience effective treatment through managedcommunications among a care team. This is accomplished in part bycreating a detailed and robust catalogue of disease-specific journeys.The platform can accurately place patients and caregivers on effectivejourneys and offer personalized guidance along those journeys based onwhere the patients are in their disease management.

For example, consider a case where a patient is diagnosed with a diseasesuch as prostate cancer. When undergoing routine screening, a patientmay have had a prostate-specific antigen (PSA) screening, as well as adigital rectal exam (DRE). An abnormal PSA screening could lead thedoctor to recommend further testing and send the patient to a specialistsuch as a urologist. The patient's pathology report may then show aGleason score of 7 (3+4), and 2 of 12 cores are positive.

This type of diagnosis could leave a patient feeling overwhelmed andscared. A caregiver, such as the patient's spouse, may start to worryabout how he or she can help the patient while the doctor is discussingthe diagnosis and treatment. The caregiver knows nothing about thisdiagnosis—only that it will test his or her ability to learn, give care,and be supportive. In these circumstances, effective communicationsbetween the patient and caregiver can make a substantial difference inthe patient's treatment.

FIG. 5 is a flowchart that illustrates a process for building journeysfor different diseases. The journeys represent particularimplementations of disease management processes. Examples of illnessesthat disease management would concern itself with would include coronaryheart disease, chronic obstructive pulmonary disease (COPD), kidneyfailure, hypertension, heart failure, obesity, diabetes mellitus,asthma, cancer, arthritis, clinical depression, sleep apnea,osteoporosis, and other common ailments. A journey is personalized for apatient and the patient's specific disease. The journeys for particulardiseases are further customized for particular patients.

In 502, the platform identifies key events of diseases. The events canbe curated manually based on research as a set of key events for one ormore diseases. Examples of key events include a schedule of treatments,medical appointments, tests, diagnostics, and any other event thatnormally occurs as part of disease management. The key events can beidentified by utilizing machine learning based on historicalinteractions of other patients with similar diseases.

In 504, the platform validates the key events with patients, caregivers,and clinicians. For example, the platform allows patients, caregivers,and clinicians to share information of hand-curated journeys that can beused to validate the key events. The patients, caregivers, andclinicians can also provide feedback to created journeys to validate thekey events.

In 506, the platform can use survey or interview data to conduct furtherresearch. The interviews can be with patients and caregivers. Theinterview data can be extracted from posts and analyzed by using naturallanguage processing to extract meaningful information. In someembodiments, the interview information could be with providers or basedon electronic medical record (EMR) data (e.g., clinical notes and claimsdata). As such, the journeys can be built and refined to improvecommunications management by the platform.

The platform stages communications and content. In one embodiment, theplatform is embodied as a system that provided a patient centricinterface for a patient and a counterpart caregiver centric interfacefor the patient's caregiver. The patient and the patient's caregiverexperience different interactive interfaces to help navigate bothindividuals along a journey of recovery in a manner that is applicableto their specific roles relative to the patient's treatment. Forexample, the platform provides different communication tools atdifferent points in the journey for the patient and caregiver whileguiding them as a care team that is collectively on the same pathtowards the patient's recovery.

The platform includes a means to facilitate exchanging communicationsbetween a patient and caregiver. For example, the patient and caregivercan install mobile apps on their handheld devices (e.g., smartphones)that present interfaces that are customized for respective roles whilekeeping the care team on a common journey towards the patient'srecovery.

FIGS. 6A through 6D show side-by-side screen views of managedcommunications that are bifurcated for a patient and the patient'scaregiver. In the illustrated embodiment, an app administered orcontrolled by the platform is running on mobile phones of the patientand the caregiver. The platform controls the communications over themobile devices via the apps to stage the way that the patient andcaregiver engage as they advance through a journey.

Each screen view is part of an interface that includes various featuresfor setup and onboarding of users and categories of features underdifferent tabs that are accessible by the care team. For example, thetabs can include an “Assistant Tab,” a “Support Tab,” and an “IntegratedDelivery System Tab.” The integrated delivery system integrates withmedical care systems to provide care delivery and health insuranceinformation for a population of patients in a defined geographic region.Each category of features includes different items to facilitatecommunications centric care. The communications are controlled to induceshared decision making where patients and family members are involved indecisions early. The decisions can relate to end of life care and canhelp a care team make appropriate treatment decisions.

Screen view 602 is an initial screen view to onboard Richard as apatient and Sarah as Richard's caregiver. This initial screen view caninclude a log-in screen that ask the patient and caregiver which rolethey have as part of a care team. The patient selects the “I'm thepatient” role, while the caregiver selects the “I'm thecaregiver/supporter” role. Once selected, the platform establishescommunications pathways for managing communications for the differentmembers of the care team. The platform processes input by the patientand caregiver in accordance with their roles at each key point along thejourney. The communications management engine can personalizecommunications for each member of the care team in accordance with theirroles.

By managing the communications in a controlled manner, the platform canensure that the patient and caregiver communicate effectively in theirrespective roles at key events along the journey. As such, the membersof the care team can collaboratively improve the health outcome of thepatient. Despite having different roles, the platform can aid eachmember to communicate effectively as a team by ensuring thatcommunications occur at a timely manner with respect to key events of ajourney.

The platform can also leverage experiences of other patients orcaregivers so that members of multiple care teams can learn from others.For example, community screen views for members of the care team can aidan individual member to identify similarly situated individuals in agroup which the care member could benefit from by joining. The platformmay identify a patient group (or form a group) with other patients thatface the same condition and decisions at the stage of recovery.Likewise, the platform may identify a caregiver group (or form a group)with other similarly situated caregivers that face similar challenges.

The platform makes it easy for the patient to connect to his medicalrecords. For example, the patient can connect the platform to hismedical records by taking a photograph of his healthcare insurance card.Screen view 604 illustrates using a smartphone's camera, on which thecare app is running, to capture an image of a healthcare insurance card.After capturing the photograph, the platform can process the image toidentify the user's EMR and access the medical records to, for example,track the user's doctor visits.

A screen view can ask the patient if he seeks assistance with a recentmedical event and include a selectable control for a diagnosis. As such,the platform utilized the patient's medical records to provide moretimely feedback rather than needing the patient to input basicinformation about his health status. The patient can confirm that hewould like assistance from the platform for his recently diagnoseddisease rather than some other medical event identified in his medicalrecords.

Screen view 608 shows an authorization screen for the patient toauthorize the caregiver. As such, a caregiver role is granted by thepatient before the caregiver can interact with the patient over theplatform in that capacity. After these initial onboarding screen views,the platform can also provide a general or role-specific tutorial toteach a care team member how to effectively utilize the platform toimprove communications as one team. The tutorial can guide the patientthrough how to use the platform. For example, the tutorial can guide thepatient to learn about tabs including an “Assistant” tab, a “Community”tab, etc.

In some embodiments, the screen views can welcome the patient withuseful information presented in a conversational format. That is, thepatient is brought into a conversation with his new health assistant.The platform starts with some information that is both reassuring andhuman. A research-based screen view of information can be provided tothe patient as well. The information could be general information ordisease-specific and/or role-specific. As such, for example, the patientcan process the information that the platform provides. When the patientsees data attributed, for example, to the American Cancer Society, thepatient starts to feel that the platform can offer credible informationto him.

The platform can also proactively ask the patient how the patient isfeeling. The patient appreciates that the platform is anticipating someof the questions that the patient has. The patient can evaluate a listof options and choose a selection. In one example, the patient selectsthe “Anxious and afraid” option. The patient's feedback aids theplatform to engage the patient in a conversational way that isempathetic to the patient's emotional and mental state.

Screen view 610 includes suggested useful next steps that leverage thecaregiver. That is, the platform is actively inducing the patient toengage the caregiver in accordance with a key point of the patient'sjourney. The engagement by the platform mimics a human's supportiveconversations.

Normally, a patient would not proactively ask the caregiver for help. Assuch, the platform serves as a bridge between the patient and thecaregiver, which encourages effective communications at particular keyevents in time. Notably, the interactions between the patient and theplatform appears on the screen view as a chat conversation that combinesfactual information, survey information, feedback, etc. that results inan overall conversational flow format.

The platform can identify a group of similarly-situated individuals thathave recently dealt with the same condition and are in the patient'sgeographic area. A screen view may include a clickable link or anothermechanism to prompt the patient to communicate with the group. Thepatient may appreciate that the group has been identified butnevertheless decide to not yet communicate with similarly-situatedpatients. Instead, the patient may want to read more about his diseaseon his own. In that case, the patient may click on a back arrow in anupper left-hand corner of a screen view to view a resource ofinformation.

Screen view 616 includes content cards that are curated for the patientbased on where the patient is on his path to recovery. Because thepatient recently received his pathology report, which is a key event,the platform has identified specific cards to help the patientunderstand his pathology report. Hence, the selection and/or combinationof content cards can be personalized for the patient and his Gleasonscore.

For a caregiver, the platform provides a series of role-specific screenviews to facilitate effective communications with the patient. Screenview 606 provides information that is specific for the caregiver andincludes relevant content from different resources. For example, thecaregiver can be alerted by the platform later that day to help thepatient to research second options. The platform can deliver a set ofuseful content cards that helps lead the caregiver to a post as aresource for a second opinion. That post is relevant to the careprovided by the caregiver to the patient.

The series of screen views allow the caregiver to quickly connect withindividuals that can offer advice based on personal experience. Forexample, the caregiver can ask questions of people linked to a postedresource. Screen view 612 shows responses from other individuals in thegroup. This allows the caregiver to get advice based on personalexperience, to provide care to the patient. The caregiver receivesresponses from a community of similarly-situated caregivers and the nameDr. Jonathan Epstein is identified. The caregiver can receive arecommendation from individuals in her geographic area to see Dr.Epstein. The caregiver can seek to find out more information about Dr.Epstein and ask the platform for help to obtain that information.

Screen view 614 shows information about Dr. Epstein. This screen viewallows the caregiver to schedule an appointment with Dr. Epstein. Theplatform then updates the content cards on her home screen with Dr.Epstein's information. A screen view can present the caregiver sharingthe latest clinical results with the platform a week later, after thevisit with Dr. Epstein.

Screen view 620 shows treatment options for the caregiver. That is, theplatform can predict treatment options at stages of the patient's pathto recovery and, as such, can preemptively pull together new content onthe topic for the caregiver and the patient. When the caregiver confirmsthe diagnosis and is ready to move on to considering treatment options,the platform can respond accordingly.

A series of screen views for the patient can identify treatment options.For example, the patient may want to learn more about FLA and roboticsurgery from individuals that have undergone similar treatment. Theplatform can find suitable individuals for the patient to connect withfor assistance. After researching his treatment options, the patient hasnarrowed his options down to FLA and robotic surgery. When the patientclicks on a Community tab, the platform auto-generates a few groups forhim: members who underwent both types of treatments recently as well asover a year ago. Over time, both the patient and caregiver develop newmindsets. The patient is accepting that he has cancer and the caregiveris more positive about helping the patient at a key moment in thepatient's life.

The screen views can connect a patient with a group, to learn what otherpatients have experienced. Through the messages from the members of thecommunity, the patient gains a beneficial perspective to face next stepsin his treatment. The patient can navigate to the Topics tab and seethat the platform has presented reluctant threads for the patient toengage. After chatting with online community members, the patient viewsthe Topics tab and sees that the platform has curated a small butrelevant set of posts for the patient at his specific stage in the pathto recovery. After getting the information that the patient andcaregiver need, they decide that FLA treatment is the best option andcan begin to prepare accordingly.

Screen view 618 is a preop screen view for the patient. That is, beforehis operation, the patient prepares for his visit via a messenger healthtab in the app.

Screen view 622 shows depicts updating content for the patient andcaregiver, after treatment screen views. During the patient's treatment,the platform continues to update content for both the patient and thecaregiver. For the patient, he sees content that helps him stay on topof his recovery process. For the caregiver, she sees content that willhelp the patient manage his side effects but also strategies to help hermaintain her personal wellness. Months later, the patient has completedtreatment and made a smooth recovery with the love and support of hisspouse due to the effective communication that was facilitated by theplatform.

Lastly, returning back to screen view of the patient, screen view 624 isfor monitoring the patient's health. As the patient continues to monitorhis health with more PSA tests, the patient is now a labelled survivorand can help others as well. The platform may connect him with otherpatients facing the same challenges and now he can be a mentor to otherpatients.

In some embodiments, aspects of the platform are integrated in othermedical care systems to provide “personalized medicine” by enablingothers to efficiently learn about the patient's disease managementprocess, obtain current information about the patient, and provideinformation to the patient about similarly situated patients, to helpidentify a suitable journey.

In one embodiment, the platform can manage the exchanges of messages ofmedical care systems to control the communication of electronic messagesfor key events. For example, the platform can message users beforescheduled visits, prompt users to review and update a profile as well asto prepare questions for healthcare professionals beforehand, providesummaries from an EMR after a patient visits a doctor, provide Googlealerts for relevant content based on preferences and interest areas,and/or prompt ongoing symptom tracking and health check-ins using shortquestions for a patient. In some embodiments, the messages can becommunicated by a home or personal virtual assistant. The platform canmanage one or more diseases for a patient via a home care managementplatform and provide users with different interfaces that depend ontheir roles in care management. For example, the patient would have auser interface tailored for a patient role, and the familial supporterwould have a user interface tailored for a supporter role.

Therefore, the platform can provide personalized guidance for patientsand caregivers with managed communications that facilitate obtaininghelp for a patient by a caregiver. This includes facilitating the way inwhich information is shared such as research insights across familymembers. This can help the group, including the patient, make difficultdecisions collaboratively.

FIG. 7 is a flowchart of a process 700 for managing communicationsbetween a patient interface on a handheld mobile device of a patient anda caregiver interface on a handheld mobile device of the caregiver. Moregenerally, the process 700 is performed by a system that implements aplatform to manage communications (e.g., in accordance with a diseasemanagement program) between a primary interface on a computing device(e.g., for a patient) and a secondary interface on a computing device(e.g., for a caregiver).

In one example, the disease management program can be selected fromamong a variety of disease management programs based oncharacteristic(s) of the patient. The system can extract thecharacteristic(s) from the EMR including a medical history (e.g.,ongoing disease) and demographics (e.g., age, gender). The EMR can beidentified based on a scanned image of a health insurance card capturedby a camera of a handheld mobile device that displays the patientinterface (see, e.g., screen view 604 of FIG. 6A). For example, ascanned image of the health insurance information can undergo an OCRprocess to extract an identifier linked to the EMR stored in a medicalrepository.

In 702, the system obtains data items (e.g., content items) that caninclude both private information and social information relating to theprimary user. In an example, the private information is obtained from aprivate source or from the primary user as input that designates a dataitem as private information. In another example, the private informationis obtained as input from the primary user that designates the data itemas private. Other examples of private information include medicalinformation from the EMR or personally identifiable information such asa social security number. Examples of social information includeinformation that users typically post on social media networks todescribe themselves to others.

The caregiver interface serves the patient interface in accordance withkey events of the disease management program. The key events can beidentified based on information of other patients that completed thedisease management program. The key events are scheduled for differentpoints in time. For example, a timeline for the key events can bedetermined based on the information of the other patients, where theinformation includes one or more key events for the disease managementprogram. The system then schedules the key events at the differentpoints in time in accordance with the timeline.

In 704, the system labels each content item as either a secure contentitem or an unsecure content item. For example, the system can labelevery content item of multiple content items with a respective label,label each content item multiple times, label only some of the multiplecontent items, etc. The secure content items include content items thatcan represent private information. The unsecure content items caninclude content items that can represent social information. Thelabeling can be based on a user designation. For example, a patient candesignate personal information as private information that should besecured or social information that can be unsecured.

In some embodiments, the labeling is based on the source of a contentitem. For example, content items sourced from an EMR can beautomatically designated as private information that should be secured.The source can include a general type of repository (e.g., hospital) ofsecure content items or a particular source associated with a policy tolabel content items as secure or unsecure. For example, a patient'sdoctor is a unique or substantially unique source (e.g., if the patienthas multiple doctors) associated with an identifier. The content itemssubmitted by the doctor are also associated with the identifier, whichis used to label the content items as secure or unsecure. The identifiercan include a unique character string or combination of terms (e.g. thedoctor's name) that can match stored identifiers in a mapping directorythat is used to label the content items.

In some embodiments, a source is based on a communication methodologyused to provide content items. That is, the manner in which contentitems are communicated can determine a label associated with the contentitems. For example, content items input by a healthcare provider througha secure portal that required login credentials can be automaticallylabeled as secure content items. On the other hand, content items thatare input through an unsecured channel where a login is not required canbe automatically labeled as unsecure content items.

The social information can be obtained from a public data source. Thesocial information can also be obtained as input from the primary userthat designates the content item as social. For example, content itemsfrom the patient's social media profile can be designated as socialinformation. Similarly, the social information can be input from thesecondary user that designates the content item as social.

Labeling a content item as a secure content item can grant control ofthe secure data to the primary user. In contrast, labeling a contentitem as an unsecure content item can include automatically enablingsharing of the unsecure data with the primary user and/or the secondaryuser.

In 706, the system compares a label of a content item with an identifierof the primary user and/or an identifier of the secondary user and withan identifier of at least one of the key events. In one example, thesystem compares the label of the content item with the identifier of thesecondary user only after comparing the label of the content item withthe identifier of the primary user. That is, the system checks whether acontent item is shareable at the key event with the primary user firstbefore checking whether the content item is shared with the secondaryuser.

In 708, the system selectively bifurcates access to the content items.In one example, the system causes display of a primary screen view of aprimary interface on a primary computing device of the primary user anda secondary screen view of a secondary interface on a secondarycomputing device of the secondary user, where the primary screen view isdifferent than the secondary screen view. The system selectivelybifurcates access to the content items for the primary interface and/orsecondary interface in accordance with a combination of one or morepaths. However, the paths are not limited to the combination(s)described herein. That is, the system selectively bifurcates access by(at least) one or more combinations of logical paths that are notlimited to a particular combination described herein. Rather, theselective bifurcation by which content items are made accessible can bedynamic to track a particular disease management program of a patient.

In 710, the system enables access to secure content items via theprimary interface (accessible by the primary user) and the secondaryinterface (accessible by the secondary user) in response to a label ofthe secure content item matching the identifier of the primary user andat a point in time in which a key event with a matching identifieroccurs (e.g., only at that time).

In 712, in response to enabling access to the secure content item, thesystem prompts an action via the primary interface and/or the secondaryinterface. The “action” can include an action for a user that isseparate from an interaction with the system. For example, the systemcan prompt the patient to modify a behavior (e.g., food consumption,exercise) or to perform another action such as scheduling an appointmentwith a doctor. Alternatively, the action can include a digitalinteraction with the system or a combination of a physical and digitalaction. For example, the action can include display on a patientinterface of a graphical control with selectable options to schedule orreschedule a key event of the disease management program.

The system can explicitly or implicitly prompt a user to perform anaction. For example, the system can prompt an action includingcommunicating a particular selectable electronic message to a computingdevice of the primary user and/or the secondary user to inputinformation related to a key event. In another example, a messaging toolis instantiated with messaging components on respective computingdevices of the primary interface and the secondary interface, and acommunications link is established between the computing devices. Assuch, the instantiation of the messaging components prompts the actionof performing a digital communication exchange.

In 714, the system enables access to unsecure content items via theprimary interface and the secondary interface in response to a label ofthe unsecure content item matching the identifier of the primary user orthe identifier of the secondary user and only at a point in time inwhich another key event with a matching identifier occurs.

In 716, in response to enabling access to the unsecure content item, thesystem prompts a communication exchange via the primary interface andthe secondary interface. For example, the system can cause a primaryscreen view to present a messaging control component on a primarycomputing device of the primary user and cause a secondary screen viewto present a counterpart messaging control component on a secondarycomputing device of the secondary user. The secondary screen view caninclude a suggested messaging topic related to the key event of theunsecure content item. For example, the caregiver's screen view can showa suggested topic for discussing a recent doctor's visit.

In 718, the system optionally causes display of the bifurcated contentitems on a first screen view of a first computing device of the primaryuser and on a second screen view of a second computing device of thesecondary user. The first screen view (e.g., patient view) is differentthan the second screen view (e.g., caregiver view). Thus, the patientand caregiver can have access to at least some of the same content itemsvia their respective interfaces.

FIG. 8 is a block diagram illustrating the platform according to someembodiments of the present disclosure. The platform 800 can includecomponents or modules that collectively operate to render screen viewson communications devices for a care team as part of communicationscentric care. A screen view is rendered in accordance withcommunications centric care processes.

A communications centric care process is conducive to interactions thatconform to an overarching objective to treat a patient. For example, acommunication-based flow can be part of a health management process(e.g., disease management). An objective may include extractinginformation about a patient's symptoms and lifestyle. The screen viewscan be rendered on a GUI of a communication device and include acombination of graphical controls and images to maintain a user'sengagement.

As used herein, a “component” or “module” may refer to a part orindependent unit of hardware and/or software that performs one or moredistinct functions. In some instances, a module is self-contained,separable, and/or interchangeable relative to other modules. As shown,the platform 800 includes one or more processors 802, a communicationmodule 804, an engagement module 806, a learning module 808, a datacollection module 810, a management module 812, and storage modules 814.Other embodiments of the platform 800 may include some of these modulesor components and/or additional modules or components that could bederived based on this disclosure or known to persons skilled in the artbut not shown herein for the sake of brevity.

The processor(s) 802 can execute modules from instructions stored instorage modules 814, which can be any device or mechanism capable ofstoring information. The communication module 804 may managecommunication between components of the platform 800 and/or between theplatform 800 and another computing device. For example, thecommunication module 804 facilitates communication of user inputs to apatient's health management program. The user inputs may be wirelesslyuploaded by the communications device (e.g., user devices 1204) or otherdevice (e.g., diverse sources 1206) over a network (e.g., network 1208)to a server computer.

The communication module 804 facilitates the exchange of communicationsbetween user devices and the management module 812, which controls theadministration of a communication flow. The communication module 804 maytransmit notifications to a user device associated with a patient orcaregiver. The user input that is communicated by the communicationmodule 804 can be stored in storage 814, one or more storage modules(e.g., storage modules 814-1 through 814-n), a remote storage accessibleto the platform 800, or a combination thereof.

The engagement module 806 can generate a flow for communication-centeredcare. The engagement module 806 also communicates user inputs todynamically adapt a communication flow to the user in real time ornear-real time. A communication flow can be rendered on a web browser,desktop software program, mobile app, over-the-top (OTT) application,etc. Accordingly, the communication flow can be rendered on a mobilephone, tablet computer, personal computer, game console (e.g., SONYPLAYSTATION or MICROSOFT XBOX), wearable electronic device (e.g., awatch or fitness tracker), network-connected “smart” device,virtual/augmented reality system (e.g., OCULUS RIFT or MICROSOFTHOLOLENS), etc.

The data collection module 810 has access to various data sources. Thesourced information is processed by the data collection module 810 inaccordance with an algorithm that can be personalized for the patientbased on instructions from a healthcare provider. For example, ahealthcare provider can select information to deliver to a user and theorder in which they should be delivered.

In some embodiments, the management module 812 can process informationderived from a data source such as devices other than the patient's userdevice. For example, a fitness tracker worn by the patient can performmachine-to-machine communications to send the patient's fitnessinformation to the management module 812 automatically (e.g., withoutuser intervention).

In some embodiments, information related to communication-centered carecan be stored in the storage modules 814 along with values calculated bythe management module 812 based on the extracted values. In this way,the management module 812 can use the stored data to improve outputs orimprove a communication flow that incorporates the obtained informationor can track a user's progress or lack thereof. In some instances, thestored data could be shared with authorized users or processed withsimilar data or information from the other users to improve operationsof the platform 800 based on the data or information of numerous users.Accordingly, the management module 812 can parse data or information andanalyze extracted values of numerous users over a period of time inorder to track the effectiveness of a management program, communicationflow, and/or surveys.

In some embodiments, the learning module 808 can utilize user inputsand/or survey information to improve the platform 800. For example, thelearning module 808 can aggregate user inputs and survey information ofnumerous patients and process the collected inputs or information toobtain insights about the effectiveness of certain modes ofinteractions, to track patients, and to adjust a communication-centeredcare algorithm. In some embodiments, the learning module 808 candiscover new techniques for improving the effectiveness of engaging withusers and improve the accuracy of existing communication flows.

For example, the learning module 808 may discover patients with certaincharacteristics. This learned data can be used to further personalizethe way that the engagement module 806 engages users. The learningmodule 808 can employ various machine learning algorithms and techniquesto improve the effectiveness of the engagement module 806 and/or datacollection module 810. Examples of machine learningalgorithms/techniques include Naïve Bayes Classifier algorithms, K MeansClustering algorithms, Support Vector Machine algorithms, linearregression, logic regression, and artificial neural networks.

In another example, communications about the patient's activities couldinclude information used to adjust a communication-centered careprocess. For example, a patient's location could be determined by theGPS receiver of the patient's smartphone. The location information canbe used to determine, for example, whether the patient is visiting ahospital. If so, the management module 812 can invoke a “welcome”narrative that includes a survey to collect basic health data about theuser and about the reason for the visit. This collected information canbe used to adjust the automated survey process.

The types of user inputs or contextual information and their sources arenot limited to the examples described herein. Instead, these examplesare illustrative of the diverse data types and sources that can beemployed to perform an automated survey process. Unlike conventionalsystems that collect limited information about a patient, the disclosedtechnology can make use of diverse data types from diverse sources toidentify how to engage a patient based on his or her particularsituation or circumstances. Although not shown nor described for thesake of brevity, the platform includes modules that ensure compliancewith privacy settings and data security.

FIG. 9 is a block diagram illustrating an example of a processing systemin which at least some operations described herein can be implemented.The processing system 900 represents a system that can run any of themethods/algorithms described above. A system may include two or moreprocessing devices such as represented in FIG. 9 , which may be coupledto each other via a network or multiple networks. A network can bereferred to as a communication network.

In the illustrated embodiment, the processing system 900 includes one ormore processors 902, memory 904, a communication device 906, and one ormore input/output (I/O) devices 908, all coupled to each other throughan interconnect 910. The interconnect 910 may be or include one or moreconductive traces, buses, point-to-point connections, controllers,adapters and/or other conventional connection devices. Each of theprocessors 902 may be or include, for example, one or moregeneral-purpose programmable microprocessors or microprocessor cores,microcontrollers, application specific integrated circuits (ASICs),programmable gate arrays, or the like, or a combination of such devices.

The processor(s) 902 control the overall operation of the processingsystem 900. Memory 904 may be or include one or more physical storagedevices, which may be in the form of random-access memory (RAM),read-only memory (ROM) (which may be erasable and programmable), flashmemory, miniature hard disk drive, or other suitable type of storagedevice, or a combination of such devices. Memory 904 may store data andinstructions that configure the processor(s) 902 to execute operationsin accordance with the techniques described above. The communicationdevice 906 may be or include, for example, an Ethernet adapter, cablemodem, Wi-Fi adapter, cellular transceiver, Bluetooth transceiver, orthe like, or a combination thereof. Depending on the specific nature andpurpose of the processing system 900, the I/O devices 908 can includedevices such as a display (which may be a touch screen display), audiospeaker, keyboard, mouse or other pointing device, microphone, camera,etc.

While processes or blocks are presented in a given order, alternativeembodiments may perform routines having steps, or employ systems havingblocks, in a different order, and some processes or blocks may bedeleted, moved, added, subdivided, combined, and/or modified to providealternative or sub-combinations, or may be replicated (e.g., performedmultiple times). Each of these processes or blocks may be implemented ina variety of different ways. In addition, while processes or blocks areat times shown as being performed in series, these processes or blocksmay instead be performed in parallel or may be performed at differenttimes. When a process or step is “based on” a value or a computation,the process or step should be interpreted as based at least on thatvalue or that computation.

Software or firmware to implement the techniques introduced here may bestored on a machine-readable storage medium and may be executed by oneor more general-purpose or special-purpose programmable microprocessors.A “machine-readable medium”, as the term is used herein, includes anymechanism that can store information in a form accessible by a machine(a machine may be, for example, a computer, network device, cellularphone, personal digital assistant (PDA), manufacturing tool, any devicewith one or more processors, etc.). For example, a machine-accessiblemedium includes recordable/non-recordable media (e.g., read-only memory(ROM), random-access memory (RAM), magnetic disk storage media, opticalstorage media, flash memory devices), etc.

Note that any and all of the embodiments described above can be combinedwith each other, except to the extent that it may be stated otherwiseabove or to the extent that any such embodiments might be mutuallyexclusive in function and/or structure. Although the present inventionhas been described with reference to specific exemplary embodiments, itwill be recognized that the invention is not limited to the embodimentsdescribed but can be practiced with modification and alteration withinthe spirit and scope of the disclosed embodiments. Accordingly, thespecification and drawings are to be regarded in an illustrative senserather than a restrictive sense.

Physical and functional components (e.g., devices, engines, modules, anddata repositories) associated with processing system 900 can beimplemented as circuitry, firmware, software, other executableinstructions, or any combination thereof. For example, the functionalcomponents can be implemented in the form of special-purpose circuitry,in the form of one or more appropriately programmed processors, a singleboard chip, a field programmable gate array, a general-purpose computingdevice configured by executable instructions, a virtual machineconfigured by executable instructions, a cloud computing environmentconfigured by executable instructions, or any combination thereof. Forexample, the functional components described can be implemented asinstructions on a tangible storage memory capable of being executed by aprocessor or other integrated circuit chip. The tangible storage memorycan be computer-readable data storage. The tangible storage memory maybe volatile or non-volatile memory. In some embodiments, the volatilememory may be considered “non-transitory” in the sense that it is not atransitory signal. Memory space and storage described in the figures canbe implemented with the tangible storage memory as well, includingvolatile or non-volatile memory.

Each of the functional components may operate individually andindependently of other functional components. Some or all of thefunctional components may be executed on the same host device or onseparate devices. The separate devices can be coupled through one ormore communication channels (e.g., wireless or wired channel) tocoordinate their operations. Some or all of the functional componentsmay be combined as one component. A single functional component may bedivided into sub-components, each sub-component performing separatemethod steps or a method step of the single component.

In some embodiments, at least some of the functional components shareaccess to a memory space. For example, one functional component mayaccess data accessed by or transformed by another functional component.The functional components may be considered “coupled” to one another ifthey share a physical connection or a virtual connection, directly orindirectly, allowing data accessed or modified by one functionalcomponent to be accessed in another functional component. In someembodiments, at least some of the functional components can be upgradedor modified remotely (e.g., by reconfiguring executable instructionsthat implement a portion of the functional components). Other arrays,systems and devices described above may include additional, fewer, ordifferent functional components for various applications.

Aspects of the disclosed embodiments may be described in terms ofalgorithms and symbolic representations of operations on data bitsstored in memory. These algorithmic descriptions and symbolicrepresentations generally include a sequence of operations leading to adesired result. The operations require physical manipulations ofphysical quantities. Usually, though not necessarily, these quantitiestake the form of electric or magnetic signals that are capable of beingstored, transferred, combined, compared, and otherwise manipulated.Customarily, and for convenience, these signals are referred to as bits,values, elements, symbols, characters, terms, numbers, or the like.These and similar terms are associated with physical quantities and aremerely convenient labels applied to these quantities.

While embodiments have been described in the context of fullyfunctioning computers, those skilled in the art will appreciate that thevarious embodiments are capable of being distributed as a programproduct in a variety of forms and that the disclosure applies equally,regardless of the particular type of machine or computer-readable mediaused to actually effect the embodiments.

The invention claimed is:
 1. A computer-implemented method performed bya system to manage communications between a patient interface on a firstcomputing device for a patient and a caregiver interface on a secondcomputing device for a caregiver of the patient, the method comprising:generating a machine learning model configured to identify a journey forthe patient from among multiple journeys, wherein the machine learningmodel includes a Naïve Bayes classifier algorithm, a k-means clusteringalgorithm, a support vector machine algorithm, or an artificial neuralnetwork; training the machine learning model based on an aggregate ofdata items of multiple patients with a disease in common with thepatient; obtaining a plurality of data items for a disease managementprogram associated with the patient; processing user-generated dataitems through the machine learning model to identify the journey for thepatient from among the multiple journeys, wherein the journey structuresa plurality of key events to stage the data items during the patient'srecovery, wherein the patient interface is served by the caregiverinterface in accordance with the plurality of key events of the journey,and wherein the plurality of key events including one or more medicaltreatments, medical appointments, or diagnostic tests scheduled to occurat different points in time; associating a data access right to each ofthe plurality of data items to designate either a secure data item or anunsecure data item based on a designation by the patient or based on asource of a data item; comparing a data access right of each of theplurality of data items with an identifier of the patient or anidentifier of the caregiver and with an identifier of at least one ofthe plurality of key events; dynamically bifurcating access to theplurality of data items for the first computing device and the secondcomputing device by: in response to a data access right of a particularsecure data item matching the identifier of the patient: granting accessto the particular secure data item on a first computing device via thepatient interface, wherein the access is granted relative to a point intime in which a key event with a matching identifier occurs, wherein thekey event is one of the plurality of key events of the journey duringthe patient's recovery as identified by the machine learning model, andprompting an action for the key event via the patient interface; inresponse to a data access right of a particular unsecure data itemmatching the identifier of the patient or the identifier of thecaregiver: granting access to the particular unsecure data item on thefirst computing device via the patient interface and the caregiverinterface on the second computing device, the access being granted atanother point in time in which another key event with a matchingidentifier occurs, and establishing a communications link for promptinga communication exchange between the first computing device and thesecond computing device over the communications link.
 2. The method ofclaim 1 further comprising: causing display of the bifurcated data itemson a first screen view of the patient interface on a first handheldmobile device and on a second screen view of the caregiver interface ona second handheld mobile device, the first screen view being differentthan the second screen view.
 3. The method of claim 1 furthercomprising, prior to obtaining the plurality of data items for thedisease management program: identifying an electronic medical record ofthe patient based on an image of a health insurance card captured by acamera of a handheld mobile device that displays the patient interface;extracting one or more characteristics of the patient from theelectronic medical record; and selecting the disease management programfrom among a plurality of disease management programs based on the oneor more characteristics.
 4. The method of claim 3 further comprising:identifying the plurality of key events based on information of otherpatients that completed the disease management program; determining atimeline for the plurality of key events based on the information of theother patients, the information of the other patients including one ormore key events for the disease management program; and scheduling theplurality of key events at the different points in time in accordancewith the timeline.
 5. A server computer that implements a communicationsmanagement protocol to share data with a primary interface on a firstcomputing device or a secondary interface on a second computing deviceserving the primary interface, the server computer comprising: at leastone memory storing: a plurality of data items associated with a primaryuser, and a plurality of key events that are scheduled to occur atdifferent points in time in accordance with a timeline that iscustomized for the primary user; and at least one processor configuredto: generate a machine learning model configured to identify theplurality of key events for the primary user, wherein the machinelearning model includes a Naïve Bayes classifier algorithm, a k-meansclustering algorithm, a support vector machine algorithm, or anartificial neural network; train the machine learning model based on anaggregate of data items of multiple users with a condition in commonwith the primary user; associate data access rights to the plurality ofdata items to designate either secure data items or unsecure data items,the data access rights being based on a user designation or a source ofa data item; compare data access rights of the plurality of data itemswith an identifier of the primary user and with an identifier of atleast one of the plurality of key events; and dynamically bifurcateaccess to the plurality of data items for the first computing device andthe second computing device by: in response to a data access right of aparticular secure data item matching the identifier of the primary user,grant access to the particular secure data item via the primaryinterface on the first computing device relative to a point in time inwhich a key event, of the plurality of key events, with a matchingidentifier occurs; and in response to grant access to the particularsecure data item, establish a communications link between the firstcomputing device or the second computing device and prompt acommunication exchange between the primary interface and the secondaryinterface.
 6. The server computer of claim 5, wherein the at least oneprocessor is further configured to: in response to a data access rightof a particular unsecure data item matching the identifier of theprimary user or an identifier of a secondary user, grant access to theparticular unsecure data items via the primary interface on the firstcomputing device and the secondary interface on the second computingdevice relative to a point in time in which another key event with amatching identifier occurs; and in response to access to the unsecuredata item being granted, prompt another communication exchange betweenthe primary interface and the secondary interface.
 7. The servercomputer of claim 6, wherein the at least one processor is furtherconfigured to: cause display of the bifurcated data items on a firstscreen view of the primary interface on the first computing device ofthe primary user and on a second screen view of the secondary interfaceon the second computing device of the secondary user, the first screenview being different than the second screen view and each presenting acontrol for exchanging communications between the primary interface andthe secondary interface.
 8. The server computer of claim 7, wherein thefirst computing device and the second computing device are eachsmartphones.
 9. A non-transitory computer-readable medium withinstructions stored thereon that, when executed by a processor, causethe processor to perform operations comprising: generating a machinelearning model configured to identify a journey for a primary user fromamong multiple journeys, wherein the machine learning model includes aNaïve Bayes classifier algorithm, a k-means clustering algorithm, asupport vector machine algorithm, or an artificial neural network;training the machine learning model based on an aggregate of data itemsof multiple users with a condition in common with the primary user;obtaining a plurality of data items that include private information andsocial information relating to a primary user; processing user-generateddata items through the machine learning model to identify the journeyfor the primary user from among the multiple journeys, wherein thejourney structures a plurality of key events to stage the data items forthe primary user, and wherein a secondary interface on a secondcomputing device serves a primary interface on a first computing devicein accordance with a communications management protocol that defines theplurality of key events of the journey; associating a data access rightto any one of the plurality of data items as either a secure data itemor an unsecure data item; comparing a data access right of the pluralityof data items with an identifier of a secondary user and with anidentifier of at least one of the plurality of key events; anddynamically bifurcating access to the plurality of data items for thefirst computing device and the second computing device in accordancewith the communications management protocol by: in response to aparticular data access right of a particular data item matching theidentifier of the secondary user and matching an identifier of a keyevent of the plurality of keys, granting access to the particular dataitem with the secondary interface on the second computing device; and inresponse to granting access to the particular data item, establishing acommunication link between the first computing device and the secondcomputing device for prompting an action related to a particular keyevent of the plurality of key events via the secondary interface on thesecond computing device.
 10. The non-transitory computer-readable mediumof claim 9, wherein the operations further comprise: in response to aparticular data access right of a particular secure data item matchingan identifier of a primary user and matching another identifier ofanother key event, granting access to a particular secure data item viathe primary interface on the first computing device.
 11. Thenon-transitory computer-readable medium of claim 9, wherein obtaining adata item of the plurality of data items comprises: extracting a privatedata item of the primary user from a private record stored in arepository of user records.
 12. The non-transitory computer-readablemedium of claim 9, wherein obtaining a data item of the plurality ofdata items comprises: receiving a data item as input to the secondaryinterface; labeling the received data item as either a secure orunsecure data item in response to a designation by the secondary user;and causing display of the received data item on a screen view of theprimary interface.
 13. The non-transitory computer-readable medium ofclaim 9, wherein obtaining a data item of the plurality of data itemscomprises: extracting a content item of the primary user from a socialmedia network; and causing display of the content item on a screen viewof the secondary interface.
 14. The non-transitory computer-readablemedium of claim 9, wherein obtaining a data item of the plurality ofdata items comprises: receiving a data item as input to the primaryinterface; and labeling the received data item as a secure data itembased on a login credential input to access the primary interface. 15.The non-transitory computer-readable medium of claim 9, whereinprompting the action for the key event comprises: communicating anelectronic message to a handheld mobile device of the primary interfaceor the secondary interface to prompt an input related to the key event.16. The non-transitory computer-readable medium of claim 9, wherein theoperations further comprise: instantiating a messaging tool on handheldmobile devices of the primary user and the secondary user.
 17. Thenon-transitory computer-readable medium of claim 9, wherein associatinga data access right to a data item to designate a secure data itemcomprises: granting control of the secure data item to the primary user.18. The non-transitory computer-readable medium of claim 9, whereinassociating a data access right to a data item to designate an unsecuredata item comprises: automatically sharing of the unsecure data with theprimary interface and the secondary interface.
 19. The non-transitorycomputer-readable medium of claim 9, wherein comparing a data accessright of a data item with the secondary user comprises: comparing thedata access right of the data item with the identifier of the secondaryuser after comparing the data access right of the data item with anidentifier of the primary user.
 20. The non-transitory computer-readablemedium of claim 9, wherein prompting the action for the particular keyevent comprises: causing display of selectable options to scheduleanother key event via the secondary interface.
 21. The non-transitorycomputer-readable medium of claim 9, wherein prompting the action forthe particular key event comprises: causing display of a messagingcontrol component on the primary interface and a counterpart messagingcontrol component on the secondary interface, the secondary interfacefurther including a suggested communication related to a matching keyevent.